The header content adds a ## Requirements section (bullet list) and terraform-docs also generates a ## Requirements section (table) later in the same injected block, which results in duplicate headings and conflicting-looking requirement info. Consider removing the Requirements block from docs/header.md (or hiding the auto-generated Requirements section in .terraform-docs.yml) so requirements are documented only once.

The README Examples section lists a basic example but links to the _examples root and the module only contains _examples/with_yaml_file. This link should be updated (likely via docs/footer.md) so the README points to real example directories.

The “Minimal usage example” is missing required module inputs. In variables.tf, both directory_roles and subscription_roles have no defaults, so omitting them will cause Terraform to fail. Update the YAML and module invocation to provide these (e.g., empty lists for a true minimal example, or a small realistic role sample).

This note says _examples/with_yaml_file is a “complete working example”, but that example currently pins azurerm to ~>3.100.0 while this module requires azurerm = 4.16.0 (provider constraint conflict). Either update the example to use a compatible provider constraint or adjust the wording so it doesn’t claim it’s working as-is.

The Examples section lists a basic example, but the link points to the _examples root and there is no basic example directory in this module (only _examples/with_yaml_file). Update the link text and URL to match the actual example folder(s).

docs/header.md doesn’t follow the repository’s module documentation standard (see CONTRIBUTING.md “Header Documentation”). The header should include a bolded module title and the expected top-level sections (e.g., ## Overview, ## Key Features, ## Basic Usage) so terraform-docs generates consistent READMEs across modules.

The generated Outputs table shows group_id description as n/a, which happens because the output "group_id" in outputs.tf has no description. Add a description to the output so the generated README contains meaningful output documentation.

The module title is formatted as bold text instead of an H1 heading. Other module docs use an H1 (e.g., modules/azure-aks/docs/header.md:1, modules/github-team/docs/header.md:1), which improves readability and consistent TOC/anchor behavior. Consider changing this first line to an H1 and regenerating the README via terraform-docs so the rendered title is consistent across modules.

The README starts with a bolded title (**Azure AD Group Module**) instead of an H1 heading. In this repo, module READMEs generally start with an H1 (see modules/aws-amq-rabbit/README.md:2, modules/azure-aks/README.md:2). Consider switching to an H1 (and ideally sourcing it from docs/header.md via terraform-docs) to keep documentation structure consistent.

This section title duplicates terraform-docs’ generated ## Resources section earlier in the README (the one listing Terraform resources/data sources). Having two ## Resources headings can be confusing and makes anchors ambiguous. Consider renaming this footer section to something like ## Remote resources (as used in other modules, e.g., modules/aws-amq-rabbit/docs/footer.md:9, modules/azure-aks/docs/footer.md:89).